-
Notifications
You must be signed in to change notification settings - Fork 209
Merge future into main
#1599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Merge future into main
#1599
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…23_09-05 Merge `main` into `future`
…25_09-04 Merge `main` into `future`
…26_09-04 Merge `main` into `future`
…01_09-05 Merge `main` into `future`
…02_09-05 Merge `main` into `future`
…03_09-04 Merge `main` into `future`
…09_09-05 Merge `main` into `future`
…10_09-05 Merge `main` into `future`
…11_09-03 Merge `main` into `future`
* rdar://149574231 (Make ProgressReporter API) (#3296) * temporarily disable flaky unit test * disable flaky tests * rerun * dirty bit clearing fix + re-enable tests
…15_09-05 Merge `main` into `future`
…17_09-05 Merge `main` into `future`
…22_09-05 Merge `main` into `future`
* Refactor Data implementation into separate chunks * Resolve availability warnings / fix non-Darwin build
* Replace inline buffer with withUnsafeTemporaryAllocation * Fix Darwin build * Move deprecated APIs off of internal implementations * Move copyBytes(to:) implementation to DataProtocol file * Don't calculate buffer length twice * Align Data mirror children size with Array
* (163828996) Remove expensive availability checks from Data replaceSubrange * Cleanup range arithmetic
…04_09-05 Merge `main` into `future`
* adopt suggestion for using keypath instead of Property.Type as argument in summary methods * rename interop methods based on api-central review * fix calling order of didSet correct calling order of didSet add missing case * rename helper methods to use update instead of updated
…05_09-05 Merge `main` into `future`
* Refactor data bridging and move to swift-foundation * Update CMake file
…07_09-05 Merge `main` into `future`
* Adopt span in Data IO implementation * Fix test failure * Fix Linux build failure * Fix Windows build * Fix FOUNDATION_FRAMEWORK build * Fix data reading for dataless files
Update lifetimes feature (future)
This reverts commit 6487b05.
…11_09-05 Merge `main` into `future`
…12_09-05 Merge `main` into `future`
Contributor
Author
|
@swift-ci please test |
itingliu
approved these changes
Nov 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that we have branched for
release/6.3, themainbranch will be tracking all work after 6.3. This merges all changes currently infuturetomain(at which point thefuturebranch will become dormant until the next release)